Since yesterday (10/21/09) some customers running the Sametime Gateway application have experienced loss of connectivity with Google.
Note: This is only for customers that had Google connectivity before and have lost it yesterday or today.
Status
10/21/09 - Sametime support reported the issue to Google.
10/22/09 - Sametime support is actively working with Google to resolve this issue.
10/23/09 - Sametime support has established the root cause of the issue. Recently Google changed the host-names of the IP's they
use for the incoming connection to the Gateway. The following is one example of the change:
Remote Host IP = 209.85.162.129" HostName = el-out-f129.google.com".
was changed to
Remote Host IP = 209.85.162.129" HostName = el-out-f129.1e100.net".
This change broke the hand-shake sequence that Sametime Gateway follows to establish the XMPP connection.
At this time Sametime team is working on a fix for the Sametime Gateway to resolve this issue. More details
about the fix and instructions to apply it will be made available here.
Thank you for your patience!
10/27/09What steps should be taken if you are experiencing this issue?
Gather and Verify the following information from your Gateway environment.
1. Sametime Gateway external Hostname & IP.
2. Email domain being used. For example @us.ibm.com
3. netstat output from the Gateway Server (XMPP Proxy server if it's a cluster)
- Open command Prompt
- Type: netstat -aon |find "5269" > netstatOutput.txt
- Submit the netstatOutput.txt
4. Re-check your firewall rules.
OutBound Connection to Google should be opened for the following IP's over Port 5269
Name: talky.l.google.com
Addresses: 64.233.169.125, 72.14.203.125, 74.125.47.125, 74.125.65.125
74.125.155.125, 209.85.137.125, 209.85.163.125, 209.85.229.125
Inbound Connection from Google should be opened for the following IP's over Port 5269
Name: talkz.l.google.com
Addresses: 74.125.154.129, 209.85.162.129, 209.85.200.129
If the problem persists please, open a new PMR with the Sametime Support team and upload the above information.
You can also track status for this issue on the Sametime Gateway Outage Wiki Page
This page will be updated when the issue is resolved.
Thank you for your patience while we work to resolve this issue.
Lotus Sametime Support Team